Tree

There is a problem

1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

1499

reference: 497-tree-1
name: 1499
tree-preservation-order: undefined
497-tpo-1
uprn
address-text
point: POINT (-0.971981 50.866704)
geometry: MULTIPOLYGON (((-0.971925 50.866698,-0.971927 50.866709,-0.971935 50.866719,-0.971947 50.866727,-0.971963 50.866732,-0.971981 50.866734,-0.971998 50.866733,-0.972014 50.866728,-0.972027 50.866720,-0.972035 50.866710,-0.972038 50.866699,-0.972036 50.866688,-0.972028 50.866678,-0.972016 50.866670,-0.972000 50.866664,-0.971982 50.866662,-0.971965 50.866664,-0.971949 50.866669,-0.971936 50.866677,-0.971928 50.866687,-0.971925 50.866698)))
notes
felled-date
entry-date: 2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

Fix the errors indicated
Use the check service to make sure the data meets the standard
Publish the updated data on the endpoint URL